Integrating SOA into an Enterprise Architecture : a comparative analysis of alternative approaches

Enterprise Architectures have emerged as comprehensive corporate artefacts that provide structure to the plethora of conceptual views on an enterprise. The recent popularity of a service-oriented design of organizations has added service and related constructs as a new element that requires consideration within an Enterprise Architecture. This paper analyzes and compares the existing proposals for how to best integrate services into Enterprise Architectures. It uses the popular Zachman Framework as an example and differentiates the existing integration alternatives. This research can be generalized beyond service integration into an investigation onto how to possibly extend Enterprise Architectures with emerging constructs.

Enterprise architecture and the integration of service-oriented architecture

In recent years, enterprise architecture (EA) has captured a growing attention as a means to systematically consolidate and interrelate diverse business and IT artefacts in order to provide holistic decision support. The recent popularity of a service-orientation has added “service “and related constructs as a new element that requires consideration within an Enterprise Architecture. Since the emergence of the Service-Oriented Architecture (SOA), many attempts have been made to incorporate SOA artefacts in existing EA frameworks. Yet, the approaches taken to achieve this goal differ substantially for the most commonly used EA frameworks to date. SOA in the context of enterprise architecture is one of the future research challenges. Several authors argue that further research is needed in order to understand how SOA impacts prior enterprise architecture frameworks. This study explores SOA integration within EA, identifies SOA integration approaches within EA and identifies factors that impact SOA integration within Enterprise Architecture.

Measuring the realization of benefits from enterprise architecture management

Enterprise architecture management (EAM) has become an intensively discussed approach to manage enterprise transformations. While many organizations employ EAM, a notable insecurity about the value of EAM remains. In this paper, we propose a model to measure the realization of benefits from EAM. We identify EAM success factors and EAM benefits through a comprehensive literature review and eleven explorative expert interviews. Based on our findings, we integrate the EAM success factors and benefits with the established DeLone & McLean IS success model resulting in a model that explains the realization of EAM benefits. This model aids organizations as a benchmark and framework for identifying and assessing the setup of their EAM initiatives and whether and how EAM benefits are materialized. We see our model also as a first step to gain insights in and start a discussion on the theory of EAM benefit realization.

Realizing benefits from enterprise architecture : a measurement model

Enterprise architecture (EA) management has become an intensively discussed approach to manage enterprise transformations. Despite the popularity and potential of EA, both researchers and practitioners lament a lack of knowledge about the realization of benefits from EA. To determine the benefits from EA, we explore the various dimensions of EA benefit realization and report on the development of a validated and robust measurement instrument. In this paper, we test the reliability and construct validity of the EA benefit realization model (EABRM), which we have designed based on the DeLone & McLean IS success model and findings from exploratory interviews. A confirmatory factor analysis confirms the existence of an impact of five distinct and individually important dimensions on the benefits derived from EA: EA artefact quality, EA infrastructure quality, EA service quality, EA culture, and EA use. The analysis presented in this paper shows that the EA benefit realization model is an instrument that demonstrates strong reliability and validity.

A comparative analysis of the integration of SOA elements in widely-used enterprise architecture frameworks

In recent years, enterprise architecture (EA) has captured increasing interest as a means to systematically consolidate and manage various enterprise artefacts in order to provide holistic decision support for business/IT alignment and business/IT landscapes management. To provide a holistic perspective on the enterprise over time, EA frameworks need to co-evolve with the changes in the enterprise and its IT over time. In this paper we focus on the emergence of Service-Oriented Architecture (SOA). There is a need to integrate SOA with EA to keep EA relevant and to use EA products to help drive successful SOA. This paper investigates and compares the integration of SOA elements in five widely used EA frameworks: Archimate, The Open Group Architecture Framework (TOGAF), Federal Enterprise Architecture Framework (FEAF), Department of Defence Architecture Framework (DoDAF) and the Ministry of Defence Architecture Framework (MODAF). It identifies what SOA elements are considered and their relative position in the overall structure. The results show that services and related elements are far from being well-integrated constructs in current EA frameworks and that the different EA frameworks integrated SOA elements in substantially different ways. Our results can support the academic EA and SOA communities with a closer and more consistent integration of EA and SOA and support practitioners in identifying an EA framework that provides the SOA support that matches their requirements.

A critical realist perspective of enterprise architecture evolution : preliminary findings

This paper investigates how Enterprise Architecture (EA) evolves due to emerging trends. It specifically explores how EA integrates the Service-oriented Architecture (SOA). Archer’s Morphogenetic theory is used as an analytical approach to distinguish the architectural conditions under which SOA is introduced, to study the relationships between these conditions and SOA introduction, and to reflect on EA evolution (elaborations) that then take place. The paper focuses on reasons for why EA evolution could take place, or not and what architectural changes could happen due to SOA integration. The research builds on sound theoretical foundations to discuss EA evolution in a field that often lacks a solid theoretical groundwork. Specifically, it proposes that critical realism, using the morphogenetic theory, can provide a useful theoretical foundation to study enterprise architecture (EA) evolution. The initial results of a literature review (a-priori model) were extended using explorative interviews. The findings of this study are threefold. First, there are five different levels of EA-SOA integration outcomes. Second, a mature EA, flexible and well-defined EA framework and comprehensive objectives of EA improve the integration outcomes. Third, the analytical separation using Archer’s theory is helpful in order to understand how these different integration outcomes are generated.

Service-oriented architecture integration within enterprise architecture : a-priori model

This paper proposes that critical realism can provide a useful theoretical foundation to study enterprise architecture (EA) evolution. Specifically it will investigate the practically relevant and academically challenging question of how EAs integrate the Service-oriented Architecture (SOA). Archer’s Morphogenetic theory is used as an analytical approach to distinguish the architectural conditions under which SOA is introduced, to study the relationships between these conditions and SOA introduction, and to reflect on EA evolution (elaborations) that then take place. The focus lies on the reasons why EA evolution takes place (or not) and what architectural changes happen. This paper uses the findings of a literature review to build an a-priori model informed by Archer’s theory to understand EA evolution in a field that often lacks a solid theoretical groundwork. The findings are threefold. First, EA can evolve on different levels (different integration outcomes). Second, the integration outcomes are classified into three levels: business architecture, information systems architecture and technology architecture. Third, the analytical separation using Archer’s theory is helpful in order to understand how these different integration outcomes are generated.

A model of enterprise architecture evolution

Enterprise architectures are exposed to fast emerging business and information technology capabilities. A prominent example is the paradigm of service-orientation, which leads to its own architectural requirements and impacts the design and ongoing evolution of Enterprise Architectures. This thesis develops the first theoretical model describing enterprise architecture evolution and outcomes in light of a changing IT landscape such as service-oriented architectures. The developed theoretical model explains enterprise architecture evolution, its main stages and related capabilities. This model can be used to derive theoretical, sound guidelines to manage enterprise architectures in a changing environment.

Applying Enterprise Architecture to Business Networks

Globalization, financial deregulation, economic turmoil, and technology breakthroughs are profoundly exposing organizations to business networks. Engaging these networks requires explicit planning from the strategic level down to the operational level of an organization, which significantly affects organizational artefacts such as business services, processes, and resources. Although enterprise architecture (EA) aligns business and IT aspects of organizational systems, previous applications of EA have not comprehensively addressed a methodological framework for planning. In the context of business networks, this study seeks to explore the application of EA for business network planning where it builds upon relevant and well-established prescriptive and descriptive aspects of EA. Prescriptive aspects include integrated models of services, business processes, and resources among other organizational artefacts, at both business and IT levels. Descriptive aspects include ontological classifications of business functionality, which allow EA models to be aligned semantically to organizational artefacts and, ultimately higher-level business strategy. A prominent approach for capturing descriptive aspects of EA is business capability modelling. In order to explore and develop the illustrative extensions of EA through capability modelling, a list of requirements (capability dimensions) for business network planning will be identified and validated through a revelatory case study encompassing different business network manifestations, or situations. These include virtual organization, liquid workforce, business network orchestration, and headquarters-subsidiary. The use of artefacts, conventionally, modelled through EA will be considered in these network situations. Two general considerations for EA extensions are explored for the identified requirements at the level of the network: extension of artefacts through the network and alignment of network level artefacts with individual organization artefacts. The list of requirements provides the basis for a constructivist extension of EA in the following ways. Firstly, for descriptive aspects, it offers constructivist insights to guide extensions for particular EA techniques and concepts. Secondly, for prescriptive aspects it defines a set of capability dimensions, which improve the analysis and assessment of organization capabilities for business network situations.

A critical realist perspective of Enterprise Architecture evolution : conditioning and outcomes

This paper investigates how Enterprise Architecture (EA) evolves due to emerging trends. It specifically explores how EA integrates the Service-oriented Architecture (SOA). Archer’s Morphogenetic theory is used as an analytical approach to distinguish the architectural conditions under which SOA is introduced, to study the relationships between these conditions and SOA introduction, and to reflect on EA evolution (elaborations) that then take place. The paper focuses on reasons for why EA evolution could take place, or not and what architectural changes could happen due to SOA integration. The research builds on sound theoretical foundations to discuss EA evolution in a field that often lacks a solid theoretical groundwork. Specifically, it proposes that critical realism, using the morphogenetic theory, can provide a useful theoretical foundation to study enterprise architecture (EA) evolution. The initial results of a literature review (a-priori model) were extended using explorative interviews. The findings of this study are threefold. First, there are five different levels of EA-SOA integration outcomes. Second, a mature EA, flexible and well-defined EA framework and comprehensive objectives of EA improve the integration outcomes. Third, the analytical separation using Archer’s theory is helpful in order to understand how these different integration outcomes are generated.

An empirical analysis of the factors and measures of Enterprise Architecture Management success

Enterprise Architecture Management (EAM) is discussed in academia and industry as a vehicle to guide IT implementations, alignment, compliance assessment, or technology management. Still, a lack of knowledge prevails about how EAM can be successfully used, and how positive impact can be realized from EAM. To determine these factors, we identify EAM success factors and measures through literature reviews and exploratory interviews and propose a theoretical model that explains key factors and measures of EAM success. We test our model with data collected from a cross-sectional survey of 133 EAM practitioners. The results confirm the existence of an impact of four distinct EAM success factors, ‘EAM product quality’, ‘EAM infrastructure quality’, ‘EAM service delivery quality’, and ‘EAM organizational anchoring’, and two important EAM success measures, ‘intentions to use EAM’ and ‘Organizational and Project Benefits’ in a confirmatory analysis of the model. We found the construct ‘EAM organizational anchoring’ to be a core focal concept that mediated the effect of success factors such as ‘EAM infrastructure quality’ and ‘EAM service quality’ on the success measures. We also found that ‘EAM satisfaction’ was irrelevant to determining or measuring success. We discuss implications for theory and EAM practice.

Empirical insights into the development of a service-oriented enterprise architecture

Organisations use Enterprise Architecture (EA) to reduce organisational complexity, improve communication, align business and information technology (IT), and drive organisational change. Due to the dynamic nature of environmental and organisational factors, EA descriptions need to change over time to keep providing value for its stakeholders. Emerging business and IT trends, such as Service-Oriented Architecture (SOA), may impact EA frameworks, methodologies, governance and tools. However, the phenomenon of EA evolution is still poorly understood. Using Archer's morphogenetic theory as a foundation, this research conceptualises three analytical phases of EA evolution in organisations, namely conditioning, interaction and elaboration. Based on a case study with a government agency, this paper provides new empirically and theoretically grounded insights into EA evolution, in particular in relation to the introduction of SOA, and describes relevant generative mechanisms affecting EA evolution. By doing so, it builds a foundation to further examine the impact of other IT trends such as mobile or cloud-based solutions on EA evolution. At a practical level, the research delivers a model that can be used to guide professionals to manage EA and continually evolve it.

Enterprise architecture – the foundation for a strategy

Artikkeli selostaa kokonaisarkkitehtuurin käsitettä ja Kansallinen digitaalinen kirjasto -hankkeen kokonaisarkkitehtuurin laatimista. Kokonaisarkkitehtuuri on tietohallinnon strategisen suunnittelun ja johtamisen väline, mutta sillä on monia käytännöllisempia käyttötarkoituksia esimerkiksi tietojärjestelmien kehittämisessä. Kansallinen digitaalinen kirjasto on opetus- ja kulttuuriministeriön tavoitteena on varmistaa kulttuurin ja tieteen digitaalisten tietovarantojen tehokas ja laadukas hallinta, jakelu ja pitkäaikaissäilytys. Lisäksi hankkeessa edistetään kulttuuriperintö- ja asiakirja-aineistojen digitointia.